@vesper8 are you using custom Eloquent Builder classes? I'd prefer to go with this soltution. What do you think?

Hrm... @antonkomarev yes actually I am using one because I also use https://github.com/MatanYadaev/laravel-eloquent-spatial

Which requires this as part of its setup

    public function newEloquentBuilder($query): SpatialBuilder
    {
        return new SpatialBuilder($query);
    }

And my models that are using this, are also Reacters or Reactants so.. if your package also starts requiring this.. I think it's going to cause a really bad conflict and I won't be able to use it.. or.. it will take some weird hacking so I can use both builders somehow?

@vesper8 that's why I'm providing this methods as trait for the Eloquent Builder, but not actually builder. This way we will be able to compose them with other methods.

I see here 2 ways:

1. Propose to author of laravel-eloquent-spatial package to move those methods to Trait and use it in Builder, to let people compose with their own builders
2. Make new Eloquent Builder in your app which will extend SpatialBuilder (since it's not final) and use traits from Love's Eloquent Builders

@antonkomarev I like that link of thinking. Worse case if I need to fork or make my own builder and extend it, that won't be an issue.. I can manage that.

In this solution I like that all these methods are placed as closer to Query Builder as possible and IDE auto-complete will work out of the box.

@vesper8 Laravel Love v9 has been released with this feature and Laravel 10 support.